System type dependent master information block (mib)

ABSTRACT

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may determine a duplexing configuration (e.g., frequency division duplexing (FDD) or time division duplexing (TDD)) of a carrier based on one or more synchronization signals. The UE may then receive a master information block (MIB) on the carrier, and may interpret one or more fields of the MIB based on the duplexing configuration of the carrier. The configuration dependent fields may include a special subframe field, a system information location field, or both. In some cases, such as in a TDD configuration, the UE may postulate a special subframe configuration of the carrier in order to receive the MIB, and may update the postulated special subframe configuration after receiving the MIB.

CROSS REFERENCES

The present application for patent claims priority to U.S. ProvisionalPatent Application No. 62/151,379 by Chen et al., entitled “System TypeDependent Master Information Block (MIB),” filed Apr. 22, 2015, assignedto the assignee hereof.

BACKGROUND

The following relates generally to wireless communication, and morespecifically to system type dependent master information blocks (MIBs).

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on.

These systems may be capable of supporting communication with multipleusers by sharing the available system resources (e.g., time, frequency,and power). Examples of such multiple-access systems include codedivision multiple access (CDMA) systems, time division multiple access(TDMA) systems, frequency division multiple access (FDMA) systems, andorthogonal frequency division multiple access (OFDMA) systems, (e.g., aLong Term Evolution (LTE) system). A wireless multiple-accesscommunications system may include a number of base stations, eachsimultaneously supporting communication for multiple communicationdevices, which may be otherwise known as user equipment (UE).

In some cases, such as when a UE is a low cost or low complexity device,a base station may transmit system information in a dedicated systeminformation message. This message may be transmitted in a shared channelwithout specifying the resources used for transmission in a controlchannel message. However, without the control channel the UE may havetrouble locating the resources used for the system information message.

SUMMARY

A user equipment (UE) may determine a duplexing configuration (e.g.,frequency division duplexing (FDD) or time division duplexing (TDD)) ofa carrier based on one or more synchronization signals. The UE may thenreceive a master information block (MIB) on the carrier, and mayinterpret one or more fields of the MIB based on the duplexingconfiguration of the carrier. The configuration dependent fields mayinclude a special subframe field, a system information location field,or both. In some cases, such as in a TDD configuration, the UE maypostulate a special subframe configuration of the carrier in order toreceive the MIB, and may update the postulated special subframeconfiguration after receiving the MIB.

A method of wireless communication is described. The method may includedetermining a duplexing configuration of a carrier, receiving a MIB onthe carrier, and interpreting at least one field of the MIB based atleast in part on the duplexing configuration of the carrier.

An apparatus for wireless communication is described. The apparatus mayinclude means for determining a duplexing configuration of a carrier,means for receiving a MIB on the carrier, and means for interpreting atleast one field of the MIB based at least in part on the duplexingconfiguration of the carrier.

A further apparatus for wireless communication is described. Theapparatus may include a processor, memory in electronic communicationwith the processor, and instructions stored in the memory and operable,when executed by the processor, to cause the apparatus to determine aduplexing configuration of a carrier, receive a MIB on the carrier, andinterpret at least one field of the MIB based at least in part on theduplexing configuration of the carrier.

A non-transitory computer-readable medium storing code for wirelesscommunication is described. The code may include instructions executableto determine a duplexing configuration of a carrier, receive a MIB onthe carrier, and interpret at least one field of the MIB based at leastin part on the duplexing configuration of the carrier.

In some examples of the method, apparatuses, or non-transitorycomputer-readable medium described herein, the duplexing configurationcomprises a time division duplex (TDD) configuration or a frequencydivision duplex (FDD) configuration. Additionally or alternatively, insome examples the at least one field of the MIB comprises a specialsubframe configuration.

In some examples of the method, apparatuses, or non-transitorycomputer-readable medium described herein, the special subframeconfiguration comprises a reduced downlink pilot time slots (DwPTS) set.Additionally or alternatively, in some examples the at least one fieldof the MIB comprises a system information block (SIB) location field.Additionally or alternatively, in some examples the at least one fieldof the MIB comprises a number of repetitions of the SIB location field.

In some examples of the method, apparatuses, or non-transitorycomputer-readable medium described herein, the SIB location field isindicative of one or more downlink (DL) subframe options for SIB1.Additionally or alternatively, some examples may include processes,features, means, or instructions for postulating a special subframeconfiguration based at least in part on the TDD configuration of thecarrier, wherein the MIB is received according to the postulated specialsubframe configuration.

In some examples of the method, apparatuses, or non-transitorycomputer-readable medium described herein, the postulated specialsubframe configuration comprises an eleven-symbol downlink pilot timeslot (DwPTS), a nine-symbol DwPTS, a one-symbol guard period, atwo-symbol uplink pilot time slot (UpPTS), or any combination thereof.Additionally or alternatively, some examples may include processes,features, means, or instructions for updating the postulated specialsubframe configuration based at least in part on the received MIB.

Some examples of the method, apparatuses, or non-transitorycomputer-readable medium described herein may further include processes,features, means, or instructions for receiving one or moresynchronization signals, wherein the duplexing configuration isdetermined based at least in part on the one or more synchronizationsignals.

A method of wireless communication is described. The method may includeidentifying a duplexing configuration of a carrier, configuring a MIBwith at least one field based at least in part on the duplexingconfiguration, and broadcasting the MIB on the carrier.

An apparatus for wireless communication is described. The apparatus mayinclude means for identifying a duplexing configuration of a carrier,means for configuring a MIB with at least one field based at least inpart on the duplexing configuration, and means for broadcasting the MIBon the carrier.

A further apparatus for wireless communication is described. Theapparatus may include a processor, memory in electronic communicationwith the processor, and instructions stored in the memory and operable,when executed by the processor, to cause the apparatus to identify aduplexing configuration of a carrier, configure a MIB with at least onefield based at least in part on the duplexing configuration, andbroadcast the MIB on the carrier.

A non-transitory computer-readable medium storing code for wirelesscommunication is described. The code may include instructions executableto identify a duplexing configuration of a carrier, configure a MIB withat least one field based at least in part on the duplexingconfiguration, and broadcast the MIB on the carrier.

Some examples of the method, apparatuses, or non-transitorycomputer-readable medium described herein may further include processes,features, means, or instructions for transmitting one or moresynchronization signals based at least in part on the duplexingconfiguration. Additionally or alternatively, in some examples theduplexing configuration comprises a TDD configuration or an FDDconfiguration.

In some examples of the method, apparatuses, or non-transitorycomputer-readable medium described herein, the at least one field of theMIB comprises a special subframe configuration. Additionally oralternatively, in some examples the at least one field of the MIBcomprises a system information block (SIB) location field. Additionallyor alternatively, in some examples the at least one field of the MIBcomprises a number of repetitions of the SIB location field.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the disclosure are described in reference to the followingfigures:

FIG. 1 illustrates an example of a wireless communications system thatsupports system type dependent master information block (MIB) operationin accordance with various aspects of the present disclosure;

FIG. 2 illustrates an example of a wireless communications subsystemthat supports system type dependent MIB operation in accordance withvarious aspects of the present disclosure;

FIG. 3 illustrates an example of a process flow that supports systemtype dependent MIB operation in accordance with various aspects of thepresent disclosure;

FIGS. 4-6 show block diagrams of a wireless device or devices thatsupports system type dependent MIB operation in accordance with variousaspects of the present disclosure;

FIG. 7 illustrates a block diagram of a system including a userequipment (UE) that supports system type dependent MIB operation inaccordance with various aspects of the present disclosure;

FIGS. 8-10 show block diagrams of a wireless device or devices thatsupport system type dependent MIB operation in accordance with variousaspects of the present disclosure;

FIG. 11 illustrates a block diagram of a system including a base stationthat supports system type dependent MIB operation in accordance withvarious aspects of the present disclosure; and

FIGS. 12-15 illustrate methods for system type dependent MIB operationin accordance with various aspects of the present disclosure.

DETAILED DESCRIPTION

Different communication types or user equipments (UEs) may becategorized based on UE capabilities. Certain categories of UE mayoperate with and benefit from utilizing different system informationblocks (SIBs) and MIBs, which may include different information dependon system or carrier type. For example, machine type communications(MTC) may be categorized as category 0. Different categories may beassociated with different channel configurations. For example, low cost,low complexity, and MTC devices may be associated with dedicated systeminformation messages and coverage enhancement techniques, and maybenefit from system dependent MIBs.

To facilitate MTC operation, bits from the MIB may be reused for MTCpurposes. Also, the MIB may be configured and interpreted based on theduplexing configuration. When determining the subframe for PBCHrepetition in a time division duplex (TDD) system, a number of factorsmay be considered. For example, PBCH repetition may avoid transmissionduring the same subframe as transmission of SIB1. In some cases, how mayDL subframes, including special subframes, are available in the cell maybe a factor in determining the subframe for PBCH repetition. Anotherfactor may be which DL subframes are configured for enhanced multimediabroadcast multicast service (eMBMS) subframes, positioning referencesignal (PRS) subframes, or other subframes. PDSCH may not be transmitteddepending on the configuration of DL subframes. It should be noted, thatwhile these techniques are discussed relating to MTC UEs, they may beused for other UEs, such as non-MTC UEs.

In a frequency division duplex (FDD) system, determining the subframefor PBCH repetition may be based on the location of SIB1 or theconfiguration of different DL subframes (e.g., which frames areconfigured for eMBMS subframes, positioning reference signals (PRS)subframes, etc.). Depending on the configuration of different DLsubframes, PDSCH may not be transmitted.

At times, SIB1 for MTC may be transmitted without a control channel.This may imply it is appropriate for the time or frequency location, theTBS of the SIB1, or the MCS of the SIB1 to have a fixed or predefinedvalue, or a value specified in the MIB. Further, complications may ariseregarding the configurations of subframes, such as MBSFN configuration,TDD configuration, etc. For example, knowledge of the location of theSIB1 may be needed to decode the SIB1, and the SIB1 may need to bedecoded to determine the subframe configurations. However, the subframeconfigurations may be beneficial in determining the location of theSIB1.

For a TDD carrier, a special subframe configuration may need to beselected to address cell coverage. For instance, large guard period,and, thus a smaller downlink pilot time slot (DwPTS), may be employed toaddress a large cell area due to large propagation delay. Or, a largeguard period may be necessary to minimize interference from other cells'DL transmissions. In some cases, a UE may be unaware of a DwPTSconfiguration before decoding a MIB. Additionally, certain factors maybe relevant to whether and when a UE may decode a MIB.

Thus, a UE may identify the system type (e.g., duplexing configuration)via one or more synchronization signals by the time the UE starts todecode PBCH. Because FDD and TDD systems may have different needs, theinformation carried in PBCH may be different (e.g., designed for the FDDor TDD system). As a result, a MIB may include some information fieldsthat are common to both TDD and FDD (e.g., information entries toindication SIB1 frequency location, time location, or TBS), and the MIBmay include some fields that are specific to (or interpreteddifferently) for FDD or TDD carriers. After a UE detects whether acarrier is FDD or TDD using PSS/SSS, and after it decodes PBCH, the UEmay interpret the PBCH content based on whether the carrier (or system)is an FDD or TDD system.

Aspects of the disclosure are initially described below in the contextof a wireless communication system. Aspects of the disclosure arefurther illustrated by and described with reference to apparatusdiagrams, system diagrams, and flowcharts that relate to system typedependent master information block (MIB).

FIG. 1 illustrates an example of a wireless communications system 100 inaccordance with various aspects of the present disclosure. The wirelesscommunications system 100 includes base stations 105, user equipment(UEs) 115, and a core network 130. In some examples, the wirelesscommunications system 100 may be a Long Term Evolution(LTE)/LTE-advanced (LTE-a) network.

Base stations 105 may wirelessly communicate with UEs 115 via one ormore base station antennas. Each base station 105 may providecommunication coverage for a respective geographic coverage area 110.Communication links 125 shown in wireless communications system 100 mayinclude uplink (UL) transmissions from a UE 115 to a base station 105,or downlink (DL) transmissions, from a base station 105 to a UE 115. UEs115 may be dispersed throughout the wireless communications system 100,and each UE 115 may be stationary or mobile. A UE 115 may also bereferred to as a mobile station, a subscriber station, a remote unit, awireless device, an access terminal, a handset, a user agent, a client,or some other suitable terminology. A UE 115 may also be a cellularphone, a wireless modem, a handheld device, a personal computer, atablet, a personal electronic device, a machine type communication (MTC)device or the like.

Some types of wireless devices may provide for automated communication.Automated wireless devices may include those implementingMachine-to-Machine (M2M) communication or Machine Type Communication(MTC). M2M or MTC may refer to data communication technologies thatallow devices to communicate with one another or a base station withouthuman intervention. For example, M2M or MTC may refer to communicationsfrom devices that integrate sensors or meters to measure or captureinformation and relay that information to a central server orapplication program that can make use of the information or present theinformation to humans interacting with the program or application. SomeUEs 115 may be MTC devices, such as those designed to collectinformation or enable automated behavior of machines. Examples ofapplications for MTC devices include smart metering, inventorymonitoring, water level monitoring, equipment monitoring, healthcaremonitoring, wildlife monitoring, weather and geological eventmonitoring, fleet management and tracking, remote security sensing,physical access control, and transaction-based business charging. An MTCdevice may operate using half-duplex (one-way) communications at areduced peak rate. MTC devices may also be configured to enter a powersaving “deep sleep” mode when not engaging in active communications.

Base stations 105 may communicate with the core network 130 and with oneanother. For example, base stations 105 may interface with the corenetwork 130 through backhaul links 132 (e.g., S1, etc.). Base stations105 may communicate with one another over backhaul links 134 (e.g., X2,etc.) either directly or indirectly (e.g., through core network 130).Base stations 105 may perform radio configuration and scheduling forcommunication with UEs 115, or may operate under the control of a basestation controller (not shown). In some examples, base stations 105 maybe macro cells, small cells, hot spots, or the like. Base stations 105may also be referred to as eNodeBs (eNBs) 105.

Base stations 105 and UE2 115 may communicate using bidirectionalcommunications based on frequency division duplexing (FDD) (e.g., usingpaired spectrum resources) or time division duplexing (TDD) operation(e.g., using unpaired spectrum resources). Frame structures for FDD(e.g., frame structure type 1) and TDD (e.g., frame structure type 2)may be defined. For TDD frame structures, each subframe may carry UL orDL traffic, and special subframes may be used to switch between DL andUL transmission. Allocation of UL and DL subframes within radio framesmay be symmetric or asymmetric and may be statically determined or maybe reconfigured semi-statically. Special subframes may carry DL or ULtraffic and may include a Guard Period (GP) between DL and UL traffic.Switching from UL to DL traffic may be achieved by setting a timingadvance at the UE 115 without the use of special subframes or a guardperiod.

UL-DL configurations with switch-point periodicity equal to the frameperiod (e.g., 10 ms) or half of the frame period (e.g., 5 ms) may alsobe supported. For example, TDD frames may include one or more specialframes, and the period between special frames may determine the TDDDL-to-UL switch-point periodicity for the frame. In some cases, certainsymbols of the special subframes may be designated for downlink use(called downlink pilot time slots (DwPTS)) and for uplink use (calleduplink pilot time slots (UpPTS)), separated by a guard symbol. Use ofTDD offers flexible deployments without requiring paired UL-DL spectrumresources. In some TDD network deployments, interference may be causedbetween UL and DL communications (e.g., interference between UL and DLcommunication from different base stations, interference between UL andDL communications from base stations and UEs, etc.). For example, wheredifferent base stations 105 serve different UEs 115 within overlappingcoverage areas according to different TDD UL-DL configurations, a UE 115attempting to receive and decode a DL transmission from a serving basestation 105 can experience interference from UL transmissions fromother, proximately located UEs 115.

A UE 115 attempting to access a wireless network may perform an initialcell search by detecting a primary synchronization signal (PSS) from abase station 105. The PSS may enable synchronization of slot timing andmay indicate a physical layer identity value. The UE 115 may thenreceive a secondary synchronization signal (SSS). The SSS may enableradio frame synchronization, and may provide a cell identity value,which may be combined with the physical layer identity value to identifythe cell. The SSS may also enable detection of a duplexing mode and acyclic prefix length. Some systems, such as time division duplex (TDD)systems, may transmit an SSS but not a PSS. Both the PSS and the SSS maybe located in the central 62 and 72 subcarriers of a carrier,respectively. After receiving the PSS and SSS, the UE 115 may receive aMIB, which may be transmitted in the physical broadcast channel (PBCH).The MIB may contain system bandwidth information, a system frame number(SFN), and a physical HARQ indicator channel (PHICH) configuration.After decoding the MIB, the UE 115 may receive one or more systeminformation block (SIBs). For example, SIB1 may contain cell accessparameters and scheduling information for other SIBs. Decoding SIB1 mayenable the UE 115 to receive SIB2. SIB2 may contain radio resourcecontrol (RRC) configuration information related to random access channel(RACH) procedures, paging, physical uplink control channel (PUCCH),physical uplink shared channel (PUSCH), power control, SRS, and cellbarring.

After completing initial cell synchronization, a UE 115 may decode theMIB, SIB1 and SIB2 prior to accessing the network. The MIB may betransmitted on PBCH and may utilize the first 4 orthogonal frequencydivision multiple access (OFDMA) symbols of the second slot of the firstsubframe of each radio frame. It may use the middle 6 resource block(RBs) (72 subcarriers) in the frequency domain. The MIB carries a fewimportant pieces of information for UE initial access, including:downlink (DL) channel bandwidth in term of RBs, PHICH configuration(duration and resource assignment), and SFN. A new MIB may be broadcastevery fourth radio frame (SFN mod 4=0) at and rebroadcast every frame(10 ms). Each repetition is scrambled with a different scrambling code.According to aspects of the present disclosure, certain fields of theMIB may be configured by a base station 105 and interpreted by a UE 115based on the duplexing configuration. For example, a TDD MIB may includefields indicative of a special subframe configuration or a SIB1location.

After reading a MIB (either a new version or a copy), the UE 115 may cantry different phases of a scrambling code until it gets a successfulcyclic redundancy check (CRC) check. The phase of the scrambling code(0, 1, 2 or 3) may enable the UE 115 to identify which of the fourrepetitions has been received. Thus, the UE 115 may determine thecurrent SFN by reading the SFN in the decoded transmission and addingthe scrambling code phase. After receiving the MIB, a UE may receive oneor more SIBs. Different SIBs may be defined according to the type ofsystem information conveyed. A new SIB1 may be transmitted in the fifthsubframe of every eighth frame (SFN mod 8=0) and rebroadcast every otherframe (20 ms). SIB1 includes access information, including cell identityinformation, and it may indicate whether a UE is allowed to camp on acell 105. SIB1 also includes cell selection information (or cellselection parameters). Additionally, SIB1 includes schedulinginformation for other SIBs. SIB2 may be scheduled dynamically accordingto information in SIB1, and includes access information and parametersrelated to common and shared channels. The periodicity of SIB2 can beset to 8, 16, 32, 64, 128, 256 or 512 radio frames.

In some cases, low cost, low complexity of MTC devices may utilize adedicated SIB, which may take the place of SIB1. This may be known as anMTC SIB, or MTC SIB1. According to the present disclosure, an MTC SIB ora default SIB1 may be located by interpreting fields of a duplexingconfiguration dependent MIB.

Accordingly, a UE 115 may determine a duplexing configuration (e.g., FDDor TDD) of a carrier based on one or more synchronization signals. TheUE 115 may then receive a MIB on the carrier, and may interpret one ormore fields of the MIB based on the duplexing configuration of thecarrier. The configuration dependent fields may include a specialsubframe field, a system information location field, or both. In somecases, such as in a TDD configuration, the UE 115 may postulate aspecial subframe configuration of the carrier in order to receive theMIB, and may update the postulated special subframe configuration afterreceiving the MIB.

FIG. 2 illustrates an example of a wireless communications subsystem 200for system type dependent MIB in accordance with various aspects of thepresent disclosure. Wireless communications subsystem 200 may include aUE 115-a and base station 105-a, which may be examples of a UE 115 basestation 105 described with reference to FIG. 1. In some cases, UE 115-amay be a low cost, low complexity or MTC device as described withreference to FIG. 1.

That is, in some systems such as an LTE system, UE 115-a may becategorized as category 0. Categories may have inherent communicationparameters. For example, category 0 may be associated with a maximum of1000 bits for a transport block size (TBS), rank 1 transmissions, onereceive antenna, and increased switching time in half-duplex, such as 1ms. In some cases, enhancements to MTC, such as enhanced MTC (eMTC), maybe supported. The enhancements may include narrowband operation, such asat 1.4 MHz with 6 resource blocks (RBs), with support for a wider systembandwidth, such as 1.4, 3, 5, 10, 15, or 20 MHz. Further, coverage maybe enhanced by as much as 15 dB.

UE 115-a and base station 105-a may communicate via communication link125-a, which may have a duplexing configuration to support both downlinkand uplink communications. For example, communication link 125-a mayhave a TDD configuration and may be divided into uplink time periods 205and downlink time periods 210.

Communication link 125-a may include a physical broadcast channel(PBCH), which may carry a master information block (MIB). In some cases,the MIB may have a defined payload size of 24 bits, without a 16 bitcyclic redundancy check (CRC). The MIB may include an 8 bit system framenumber, a 4 bit system bandwidth indicator, a 2 bit physical hybrid-ARQindicator channel (PHICH) resource indicator, a 1 bit PHICH time-spanindicator, and 9 reserved bits.

To enhance coverage, the PBCH may be repeated over different subframes.By repeating the PBCH over different subframes, UEs 115 in bad radiochannel conditions may be covered. For example, the PBCH may be repeatedin subframe 0 and at least one other subframe, for all frames. Framesmay be transmitted in 40 ms cycles if repetition is configured. In somecases, the network may determine whether to configure PBCH repetitionsfor a cell. The PBCH repetition configuration may be a long-termproperty of the cell. As such, in some cases, UE 115-a may assume thePBCH repetition is the same, whether on or off, during subsequent timeswaking up during initial acquisition.

To facilitate MTC operation, bits from the MIB may be reused for MTCpurposes. For example, the 9 reserved bits of the MIB may be used forMTC. Use of the 9 reserved bits may include 1 bit indicating support ofcoverage enhancement, 1 bit indicating support of release 13 MTC UE, 2or 3 bits indicating the time frequency position of a MTC SIB1, 2 bitsindicating a TBS of a MTC SIB1, 2 bits for a control format indicator(CFI), or a combination thereof. In some cases, it may be desired toreserve a number of the 9 reserved bits for future use. For example, MTCuse of the 9 reserved bits may be limited to 4 or 5 of the potential 9bits.

When determining the subframe for PBCH repetition in a time divisionduplex (TDD) system, a number of factors may be considered. For example,PBCH repetition may avoid transmission during the same subframe astransmission of SIB1. SIB1 may be transmitted in the center 6 RBs. Insome cases, SIB1 transmission may perform subband hopping, such as toexploit frequency diversity gain, which may allow PBCH repetition to usethe center 6 RBs. Further, if downlink pilot time slot (DwPTS) isavailable for physical downlink shared channel (PDSCH) transmission, theDwPTS may have a length of 3 symbols and PDSCH transmissions may beavoided. In some cases, how may DL subframes, including specialsubframes, are available in the cell may be a factor in determining thesubframe for PBCH repetition. Another factor may be which DL subframesare configured for enhanced multimedia broadcast multicast service(eMBMS) subframes, positioning reference signal (PRS) subframes, orother subframes. PDSCH may not be transmitted depending on theconfiguration of DL subframes.

In a frequency division duplex (FDD) system (not shown), determining thesubframe for PBCH repetition may be based on the location of SIB1 or theconfiguration of different DL subframes (e.g., which frames areconfigured for eMBMS subframes, PRS subframes, etc.). Depending on theconfiguration of different DL subframes, PDSCH may not be transmitted.

At times, SIB1 for MTC may be transmitted by base station 105-a withouta control channel. This may necessitate the time or frequency location,the TBS of the SIB1, or the MCS of the SIB1 to have a fixed orpredefined value, or a value specified in the MIB. Further,complications may arise regarding the configurations of subframes, suchas MBSFN configuration, TDD configuration, etc. For example, knowledgeof the location of the SIB1 may be needed to decode the SIB1, and theSIB1 may need to be decoded to determine the subframe configurations.However, the subframe configurations may be beneficial in determiningthe location of the SIB1.

In some cases, PBCH may be repeated within a frame. For example, PBCHmay be transmitted in subframe 0 and in at least one other subframe ofeach frame, and it may be repeated in a 40 ms cycle. For FDD carriers,PBCH may be repeated in subframe 9, which may assist with coherent PBCHdetection (e.g., because PBCH would be transmitted in consecutivesubframes 0 and 9). For TDD carriers, PBCH may be repeated in subframe1, which may assist with coherent PBCH detection (e.g., because PBCHwould be transmitted in consecutive subframes 0 and 1).

For a TDD carrier, a DwPTS configuration may need to be selected toaddress cell coverage. For instance, large guard period, and, thus asmaller DwPTS, may be employed to address a large cell area (which maybe a subset of coverage area 110-a) due to large propagation delay. Or,a large guard period may be necessary to minimize interference fromother cells' DL transmissions.

In some cases, UE 115-a may be unaware of a DwPTS configuration beforedecoding a MIB. Additionally, certain factors may be relevant to whetherand when UE 115-a may decode a MIB. A MIB may be present in the center 6RBs. In some cases, if DL to UL interference is a concern, ULtransmissions may not be scheduled in the center 6 RBs in subframe 1 or2, or both. Or, if a large UL timing advance is employed for a decodingthe MIB, UE 115-a, after decoding MIB and SIB1, may be scheduled inother UL subframes, or may not decode the MIB and may be scheduled insubframes 1 or 2. In view of this, if subframe 1 is used for MIBrepetition, UE 115-a may assume a fixed DwPTS configuration (e.g.,11-symbol DwPTS for normal CP, 9-symbol DwPTS for extended CP; 1-symbolguard period; 2-symbol UpPTS). Once MIB or SIB1 have been decoded, UE115-a may know an actual DwPTS length, which may be different form theassumed DwPTS configuration. But in some cases, this difference may beinconsequential. For regular traffic, UE 115-a may use the actualconfiguration; for MIB detection, UE 115-a may assume and use the fixedconfiguration.

UE 115-a may identify the system type (e.g., duplexing configuration)via PSS/SSS by the time UE 115-a starts to decode PBCH. Because FDD andTDD systems may have different needs, the information carried in PBCHmay be different (e.g., designed for the FDD or TDD system). As aresult, a MIB may include some information fields that are common toboth TDD and FDD (e.g., information entries to indication SIB1 frequencylocation, time location, or TBS), and the MIB may include some fieldsthat are specific to (or interpreted differently) for FDD or TDDcarriers. After UE 115-a detects whether a carrier is FDD or TDD usingPSS/SSS, and after it decodes PBCH, UE 115-a may interpret the PBCHcontent based on whether the carrier (or system) is an FDD or TDDsystem.

In some cases, a field of the MIB may be used to indicate a DwPTSconfiguration (e.g., 1-bit to indicate a reduced set of entries ofDWPTS, such as 3 or 11 symbols). It may also include informationregarding DL subframe availability. For instance, 1-bit may indicatewhether UE 115-a can assume the following possible DL subframes forSIB1:0 may indicate the possible DL subframes are 0 and 5, while 1 mayindicate the possible DL subframes are 9, 4, 5, and 9. This mayrepresent the common set of DL subframes for TDD configurations #1, #2,#4, and #5. In some cases, such indications may be implicit. Forexample, base station 105-a may indicate that SIB1 is present insubframe 4. In some cases, FDD-specific MIBs may also have reserved bitsthat correspond to reserved TDD-specific information.

FIG. 3 illustrates an example of a process flow 300 for system typedependent MIB in accordance with various aspects of the presentdisclosure. Process flow 300 may include a UE 115-b and base station105-b, which may be examples of a UE 115 and base station 105 describedwith reference to FIGS. 1-2.

At 305, base station 105-b may broadcast synchronization signals such asa PSS or SSS. In some cases, base station 105-b may transmit one or moresynchronization signals based at least in part on the duplexingconfiguration. UE 115-b may receive the one or more synchronizationsignals, such that the duplexing configuration is determined based atleast in part on the one or more synchronization signals. In some cases,base station 105-b may identify a duplexing configuration of a carrierprior to transmitting the PSS/SSS.

At 310, UE 115-b may determine a duplexing configuration of the carrierbased on the synchronization signals. In some examples the duplexingconfiguration comprises a TDD configuration. UE 115-b may postulate aspecial subframe configuration based at least in part on the TDDconfiguration of the carrier, such that a MIB is received according tothe postulated special subframe configuration. In some examples thepostulated special subframe configuration comprises an eleven-symbolDwPTS, a nine-symbol DwPTS, a one-symbol guard period, a two-symbolUpPTS, or any combination thereof.

At 315, base station 105-b may broadcast a MIB. That is, Base station105-b may broadcast the MIB on the carrier and UE 115-b may receive theMIB on the carrier. Base station 105-b may configure the MIB with atleast one field based at least in part on the duplexing configuration.

At 320, UE 115-b may interpret the MIB based on the duplexingconfiguration. That is, UE 115-b may interpret at least one field of theMIB based at least in part on the duplexing configuration of thecarrier. In some examples the at least one field of the MIB comprises aspecial subframe configuration. In some examples the special subframeconfiguration comprises a reduced DwPTS set. In some examples the atleast one field of the MIB comprises a SIB location field. In someexamples, the at least one field of the MIB comprises a number ofrepetitions of the SIB location field. In some examples the SIB locationfield is indicative of one or more DL subframe options for SIB1. In somecases, UE 115-b may then update the postulated special subframeconfiguration based at least in part on the received MIB.

At 325, UE 115-b may identify the location or other aspects of a SIB1(such as transport block size and modulation and coding scheme (MCS))based on the MIB. At 330, base station 105-b may transmit SIB1 in ashared channel. In some case the SIB may be an MTC SIB1.

FIG. 4 shows a block diagram of a wireless device 400 configured forsystem type dependent MIB in accordance with various aspects of thepresent disclosure. Wireless device 400 may be an example of aspects ofa UE 115 described with reference to FIGS. 1-3.

Wireless device 400 may include a receiver 405, a system type dependentMIB module 410, or a transmitter 415. Wireless device 400 may alsoinclude a processor. Each of these components may be in communicationwith each other.

The receiver 405 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to system typedependent MIB, etc.). Information may be passed on to the system typedependent MIB module 410, and to other components of wireless device400.

The system type dependent MIB module 410 may determine a duplexingconfiguration of a carrier, receive a MIB on the carrier, and interpretat least one field of the MIB based at least in part on the duplexingconfiguration of the carrier.

The transmitter 415 may transmit signals received from other componentsof wireless device 400. In some examples, the transmitter 415 may becollocated with the receiver 405 in a transceiver module. Thetransmitter 415 may include a single antenna, or it may include aplurality of antennas.

FIG. 5 shows a block diagram of a wireless device 500 for system typedependent MIB in accordance with various aspects of the presentdisclosure. Wireless device 500 may be an example of aspects of awireless device 400 or a UE 115 described with reference to FIGS. 1-4.Wireless device 500 may include a receiver 405-a, a system typedependent MIB module 410-a, or a transmitter 415-a. Wireless device 500may also include a processor. Each of these components may be incommunication with each other. The system type dependent MIB module410-a may also include a duplexing configuration module 505, a MIBmodule 510, and a MIB interpretation module 515.

The receiver 405-a may receive information which may be passed on tosystem type dependent MIB module 410-a, and to other components ofwireless device 500. The system type dependent MIB module 410-a mayperform the operations described with reference to FIG. 4. Thetransmitter 415-a may transmit signals received from other components ofwireless device 500.

The duplexing configuration module 505 may determine a duplexingconfiguration of a carrier as described with reference to FIGS. 2-3.

The MIB module 510 may receive a MIB on the carrier as described withreference to FIGS. 2-3.

The MIB interpretation module 515 may interpret at least one field ofthe MIB based at least in part on the duplexing configuration of thecarrier as described with reference to FIGS. 2-3.

FIG. 6 shows a block diagram 600 of a system type dependent MIB module410-b which may be a component of a wireless device 400 or a wirelessdevice 500 for system type dependent MIB in accordance with variousaspects of the present disclosure. The system type dependent MIB module410-b may be an example of aspects of a system type dependent MIB module410 described with reference to FIGS. 4-5. The system type dependent MIBmodule 410-b may include a duplexing configuration module 505-a, a MIBmodule 510-a, and a MIB interpretation module 515-a. Each of thesemodules may perform the functions described with reference to FIG. 5.The system type dependent MIB module 410-b may also include a TDD module605, a special subframe module 610, a SIB location module 615, and asynchronization module 620.

The TDD module 605 may be configured such that the duplexingconfiguration may include a TDD configuration as described withreference to FIGS. 2-3.

The special subframe module 610 may be configured such that the at leastone field of the MIB may include a special subframe configuration asdescribed with reference to FIGS. 2-3. In some examples, the specialsubframe configuration comprises a reduced downlink pilot time slots(DwPTS) set. The special subframe module 610 may also postulate aspecial subframe configuration based at least in part on the TDDconfiguration of the carrier, such that the MIB is received according tothe postulated special subframe configuration. In some examples, thepostulated special subframe configuration comprises an eleven-symboldownlink pilot time slot (DwPTS), a nine-symbol DwPTS, a one-symbolguard period, a two-symbol uplink pilot time slot (UpPTS), or anycombination thereof. The special subframe module 610 may also update thepostulated special subframe configuration based at least in part on thereceived MIB.

The SIB location module 615 may be configured such that the at least onefield of the MIB may include a SIB location field as described withreference to FIGS. 2-3. In some examples, the SIB location field may beindicative of one or more DL subframe options for SIB1.

The synchronization module 620 may receive one or more synchronizationsignals, such that the duplexing configuration is determined based atleast in part on the one or more synchronization signals as describedwith reference to FIGS. 2-3.

FIG. 7 shows a diagram of a system 700 including a UE 115 configured forsystem type dependent MIB in accordance with various aspects of thepresent disclosure. System 700 may include UE 115-c, which may be anexample of a wireless device 400, a wireless device 500, or a UE 115described with reference to FIGS. 1, 2 and 4-6. UE 115-c may include asystem type dependent MIB module 710, which may be an example of asystem type dependent MIB module 410 described with reference to FIGS.4-6. UE 115-c may also include an MTC module 725. UE 115-c may alsoinclude components for bi-directional voice and data communicationsincluding components for transmitting communications and components forreceiving communications. For example, UE 115-c may communicatebi-directionally with base station 105-c.

MTC module 725 may enable MTC specific procedures as described withreference to FIG. 1. MTC module 725 may also enable additional powersaving and coverage enhancement features such as narrowband operationand additional redundancy.

UE 115-c may also include a processor 705, and memory 715 (includingsoftware (SW)) 720, a transceiver 735, and one or more antenna(s) 740,each of which may communicate, directly or indirectly, with one another(e.g., via buses 745). The transceiver 735 may communicatebi-directionally, via the antenna(s) 740 or wired or wireless links,with one or more networks, as described above. For example, thetransceiver 735 may communicate bi-directionally with a base station 105or another UE 115. The transceiver 735 may include a modem to modulatethe packets and provide the modulated packets to the antenna(s) 740 fortransmission, and to demodulate packets received from the antenna(s)740. While UE 115-c may include a single antenna 740, UE 115-c may alsohave multiple antennas 740 capable of concurrently transmitting orreceiving multiple wireless transmissions.

The memory 715 may include random access memory (RAM) and read onlymemory (ROM). The memory 715 may store computer-readable,computer-executable software/firmware code 720 including instructionsthat, when executed, cause the processor 705 to perform variousfunctions described herein (e.g., system type dependent MIB, etc.).Alternatively, the software/firmware code 720 may not be directlyexecutable by the processor 705 but cause a computer (e.g., whencompiled and executed) to perform functions described herein. Theprocessor 705 may include an intelligent hardware device, (e.g., acentral processing unit (CPU), a microcontroller, an applicationspecific integrated circuit (ASIC), etc.)

FIG. 8 shows a block diagram of a wireless device 800 configured forsystem type dependent MIB in accordance with various aspects of thepresent disclosure. Wireless device 800 may be an example of aspects ofa base station 105 described with reference to FIGS. 1-7. Wirelessdevice 800 may include a receiver 805, a base station system typedependent MIB module 810, or a transmitter 815. Wireless device 800 mayalso include a processor. Each of these components may be incommunication with each other.

The receiver 805 may receive information such as packets, user data, orcontrol information associated with various information channels (e.g.,control channels, data channels, and information related to system typedependent MIB, etc.). Information may be passed on to the base stationsystem type dependent MIB module 810, and to other components ofwireless device 800.

The base station system type dependent MIB module 810 may identify aduplexing configuration of a carrier, configure a MIB with at least onefield based at least in part on the duplexing configuration, andbroadcast the MIB on the carrier.

The transmitter 815 may transmit signals received from other componentsof wireless device 800. In some examples, the transmitter 815 may becollocated with the receiver 805 in a transceiver module. Thetransmitter 815 may include a single antenna, or it may include aplurality of antennas. In some examples, the transmitter 815 maybroadcast the MIB on the carrier.

FIG. 9 shows a block diagram of a wireless device 900 for system typedependent MIB in accordance with various aspects of the presentdisclosure. Wireless device 900 may be an example of aspects of awireless device 800 or a base station 105 described with reference toFIGS. 1-8. Wireless device 900 may include a receiver 805-a, a basestation system type dependent MIB module 810-a, or a transmitter 815-a.Wireless device 900 may also include a processor. Each of thesecomponents may be in communication with each other. The base stationsystem type dependent MIB module 810-a may also include a BS duplexingconfiguration module 905, and a MIB configuration module 910.

The receiver 805-a may receive information which may be passed on tobase station system type dependent MIB module 810-a, and to othercomponents of wireless device 900. The base station system typedependent MIB module 810-a may perform the operations described withreference to FIG. 8. The transmitter 815-a may transmit signals receivedfrom other components of wireless device 900.

The BS duplexing configuration module 905 may identify a duplexingconfiguration of a carrier as described with reference to FIGS. 2-3.

The MIB configuration module 910 may configure a MIB with at least onefield based at least in part on the duplexing configuration as describedwith reference to FIGS. 2-3.

FIG. 10 shows a block diagram 1000 of a base station system typedependent MIB module 810-b which may be a component of a wireless device800 or a wireless device 900 for system type dependent MIB in accordancewith various aspects of the present disclosure. The base station systemtype dependent MIB module 810-b may be an example of aspects of a basestation system type dependent MIB module 810 described with reference toFIGS. 8-9. The base station system type dependent MIB module 810-b mayinclude a BS duplexing configuration module 905-a, and a MIBconfiguration module 910-a. Each of these modules may perform thefunctions described with reference to FIG. 9. The base station systemtype dependent MIB module 810-b may also include a BS synchronizationmodule 1005, a BS TDD module 1010, a BS special subframe module 1015,and a BS SIB location module 1020.

The BS synchronization module 1005 may transmit one or moresynchronization signals based at least in part on the duplexingconfiguration as described with reference to FIGS. 2-3.

The BS TDD module 1010 may be configured such that the duplexingconfiguration may include a TDD configuration as described withreference to FIGS. 2-3.

The BS special subframe module 1015 may be configured such that the atleast one field of the MIB may include a special subframe configurationas described with reference to FIGS. 2-3.

The BS SIB location module 1020 may be configured such that the at leastone field of the MIB may include a SIB location field as described withreference to FIGS. 2-3.

FIG. 11 shows a diagram of a system 1100 including a base station 105configured for system type dependent MIB in accordance with variousaspects of the present disclosure. System 1100 may include base station105-d, which may be an example of a wireless device 800, a wirelessdevice 900, or a base station 105 described with reference to FIGS. 1, 2and 8-10. Base station 105-d may include a base station system typedependent MIB module 1110, which may be an example of a base stationsystem type dependent MIB module 810 described with reference to FIGS.8-10. Base station 105-d may also include components for bi-directionalvoice and data communications including components for transmittingcommunications and components for receiving communications. For example,base station 105-d may communicate bi-directionally with UE 115-d and UE115-e (which may be an MTC device).

In some cases, base station 105-d may have one or more wired backhaullinks. Base station 105-d may have a wired backhaul link (e.g., S1interface, etc.) to the core network 130. Base station 105-d may alsocommunicate with other base stations 105, such as base station 105-e andbase station 105-f via inter-base station backhaul links (e.g., an X2interface). Each of the base stations 105 may communicate with UEs 115using the same or different wireless communications technologies. Insome cases, base station 105-d may communicate with other base stationssuch as 105-e or 105-f utilizing base station communication module 1125.In some examples, base station communication module 1125 may provide anX2 interface within a Long Term Evolution (LTE)/LTE-A wirelesscommunication network technology to provide communication between someof the base stations 105. In some examples, base station 105-d maycommunicate with other base stations through core network 130. In somecases, base station 105-d may communicate with the core network 130through network communications module 1130.

The base station 105-d may include a processor 1105, memory 1115(including software (SW)1120), transceiver 1135, and antenna(s) 1140,which each may be in communication, directly or indirectly, with oneanother (e.g., over bus system 1145). The transceivers 1135 may beconfigured to communicate bi-directionally, via the antenna(s) 1140,with the UEs 115, which may be multi-mode devices. The transceiver 1135(or other components of the base station 105-d) may also be configuredto communicate bi-directionally, via the antennas 1140, with one or moreother base stations (not shown). The transceiver 1135 may include amodem configured to modulate the packets and provide the modulatedpackets to the antennas 1140 for transmission, and to demodulate packetsreceived from the antennas 1140. The base station 105-d may includemultiple transceivers 1135, each with one or more associated antennas1140. The transceiver may be an example of a combined receiver 805 andtransmitter 815 of FIG. 8.

The memory 1115 may include RAM and ROM. The memory 1115 may also storecomputer-readable, computer-executable software code 1120 containinginstructions that are configured to, when executed, cause the processor1105 to perform various functions described herein (e.g., system typedependent MIB, selecting coverage enhancement techniques, callprocessing, database management, message routing, etc.). Alternatively,the software 1120 may not be directly executable by the processor 1105but be configured to cause the computer, e.g., when compiled andexecuted, to perform functions described herein. The processor 1105 mayinclude an intelligent hardware device, e.g., a CPU, a microcontroller,an ASIC, etc. The processor 1105 may include various special purposeprocessors such as encoders, queue processing modules, base bandprocessors, radio head controllers, digital signal processor (DSPs), andthe like.

The base station communications module 1125 may manage communicationswith other base stations 105. In some cases, a communications managementmodule may include a controller or scheduler for controllingcommunications with UEs 115 in cooperation with other base stations 105.For example, the base station communications module 1125 may coordinatescheduling for transmissions to UEs 115 for various interferencemitigation techniques such as beamforming or joint transmission.

The components of wireless device 400, wireless device 500, system typedependent MIB module 410, wireless device 800, wireless device 900, basestation system type dependent MIN module 810, system 700, and system 100may, individually or collectively, be implemented with at least one ASICadapted to perform some or all of the applicable functions in hardware.Alternatively, the functions may be performed by one or more otherprocessing units (or cores), on at least one IC. In other examples,other types of integrated circuits may be used (e.g.,Structured/Platform ASICs, a field programmable gate array (FPGA), oranother semi-custom IC), which may be programmed in any manner known inthe art. The functions of each unit may also be implemented, in whole orin part, with instructions embodied in a memory, formatted to beexecuted by one or more general or application-specific processors.

FIG. 12 shows a flowchart illustrating a method 1200 for system typedependent MIB in accordance with various aspects of the presentdisclosure. The operations of method 1200 may be implemented by a UE 115or its components as described with reference to FIGS. 1-11. Forexample, the operations of method 1200 may be performed by the systemtype dependent MIB module 410 as described with reference to FIGS. 4-7.In some examples, a UE 115 may execute a set of codes to control thefunctional elements of the UE 115 to perform the functions describedbelow. Additionally or alternatively, the UE 115 may perform aspects thefunctions described below using special-purpose hardware.

At block 1205, the UE 115 may determine a duplexing configuration of acarrier as described with reference to FIGS. 2-3. In certain examples,the operations of block 1205 may be performed by the duplexingconfiguration module 505 as described with reference to FIG. 5.

At block 1210, the UE 115 may receive a MIB on the carrier as describedwith reference to FIGS. 2-3. In certain examples, the operations ofblock 1210 may be performed by the MIB module 510 as described withreference to FIG. 5.

At block 1215, the UE 115 may interpret at least one field of the MIBbased at least in part on the duplexing configuration of the carrier asdescribed with reference to FIGS. 2-3. In certain examples, theoperations of block 1215 may be performed by the MIB interpretationmodule 515 as described with reference to FIG. 5.

FIG. 13 shows a flowchart illustrating a method 1300 for system typedependent MIB in accordance with various aspects of the presentdisclosure. The operations of method 1300 may be implemented by a UE 115or its components as described with reference to FIGS. 1-11. Forexample, the operations of method 1300 may be performed by the systemtype dependent MIB module 410 as described with reference to FIGS. 4-7.In some examples, a UE 115 may execute a set of codes to control thefunctional elements of the UE 115 to perform the functions describedbelow. Additionally or alternatively, the UE 115 may perform aspects thefunctions described below using special-purpose hardware. The method1300 may also incorporate aspects of method 1200 of FIG. 12.

At block 1305, the UE 115 may determine a duplexing configuration of acarrier as described with reference to FIGS. 2-3. In certain examples,the operations of block 1305 may be performed by the duplexingconfiguration module 505 as described with reference to FIG. 5.

At block 1310, the UE 115 may postulate a special subframe configurationbased at least in part on the TDD configuration of the carrier, suchthat a MIB is received according to the postulated special subframeconfiguration as described with reference to FIGS. 2-3. In certainexamples, the operations of block 1310 may be performed by the specialsubframe module 610 as described with reference to FIG. 6.

At block 1315, the UE 115 may receive a MIB on the carrier as describedwith reference to FIGS. 2-3. In certain examples, the operations ofblock 1315 may be performed by the MIB module 510 as described withreference to FIG. 5.

At block 1320, the UE 115 may interpret at least one field of the MIBbased at least in part on the duplexing configuration of the carrier asdescribed with reference to FIGS. 2-3. In certain examples, theoperations of block 1320 may be performed by the MIB interpretationmodule 515 as described with reference to FIG. 5.

At block 1325, the UE 115 may update the postulated special subframeconfiguration based at least in part on the received MIB as describedwith reference to FIGS. 2-3. In certain examples, the operations ofblock 1325 may be performed by the special subframe module 610 asdescribed with reference to FIG. 6.

FIG. 14 shows a flowchart illustrating a method 1400 for system typedependent MIB in accordance with various aspects of the presentdisclosure. The operations of method 1400 may be implemented by a UE 115or its components as described with reference to FIGS. 1-11. Forexample, the operations of method 1400 may be performed by the systemtype dependent MIB module 410 as described with reference to FIGS. 4-7.In some examples, a UE 115 may execute a set of codes to control thefunctional elements of the UE 115 to perform the functions describedbelow. Additionally or alternatively, the UE 115 may perform aspects thefunctions described below using special-purpose hardware. The method1400 may also incorporate aspects of methods 1200, and 1300 of FIGS.12-13.

At block 1405, the UE 115 may receive one or more synchronizationsignals, such that a duplexing configuration is determined based atleast in part on the one or more synchronization signals as describedwith reference to FIGS. 2-3. In certain examples, the operations ofblock 1405 may be performed by the synchronization module 620 asdescribed with reference to FIG. 6.

At block 1410, the UE 115 may determine a duplexing configuration of acarrier as described with reference to FIGS. 2-3. In certain examples,the operations of block 1410 may be performed by the duplexingconfiguration module 505 as described with reference to FIG. 5.

At block 1415, the UE 115 may receive a MIB on the carrier as describedwith reference to FIGS. 2-3. In certain examples, the operations ofblock 1415 may be performed by the MIB module 510 as described withreference to FIG. 5.

At block 1420, the UE 115 may interpret at least one field of the MIBbased at least in part on the duplexing configuration of the carrier asdescribed with reference to FIGS. 2-3. In certain examples, theoperations of block 1420 may be performed by the MIB interpretationmodule 515 as described with reference to FIG. 5.

FIG. 15 shows a flowchart illustrating a method 1500 for system typedependent MIB in accordance with various aspects of the presentdisclosure. The operations of method 1500 may be implemented by a basestation 105 or its components as described with reference to FIGS. 1-11.For example, the operations of method 1500 may be performed by the basestation system type dependent MIB module 810 as described with referenceto FIGS. 8-11. In some examples, a base station 105 may execute a set ofcodes to control the functional elements of the base station 105 toperform the functions described below. Additionally or alternatively,the base station 105 may perform aspects the functions described belowusing special-purpose hardware. The method 1500 may also incorporateaspects of methods 1200, 1300, and 1400 of FIGS. 12-14.

At block 1505, the base station 105 may identify a duplexingconfiguration of a carrier as described with reference to FIGS. 2-3. Incertain examples, the operations of block 1505 may be performed by theBS duplexing configuration module 905 as described with reference toFIG. 9.

At block 1510, the base station 105 may configure a MIB with at leastone field based at least in part on the duplexing configuration asdescribed with reference to FIGS. 2-3. In certain examples, theoperations of block 1510 may be performed by the MIB configurationmodule 910 as described with reference to FIG. 9.

At block 1515, the base station 105 may broadcast the MIB on the carrieras described with reference to FIGS. 2-3. In certain examples, theoperations of block 1515 may be performed by the transmitter 815 asdescribed with reference to FIG. 8.

Thus, methods 1200, 1300, 1400, and 1500 may provide for system typedependent MIB. It should be noted that methods 1200, 1300, 1400, and1500 describe possible implementation, and that the operations and thesteps may be rearranged or otherwise modified such that otherimplementations are possible. In some examples, aspects from two or moreof the methods 1200, 1300, 1400, and 1500 may be combined.

The description herein provides examples, and is not limiting of thescope, applicability, or examples set forth in the claims. Changes maybe made in the function and arrangement of elements discussed withoutdeparting from the scope of the disclosure. Various examples may omit,substitute, or add various procedures or components as appropriate.Also, features described with respect to some examples may be combinedin other examples.

Techniques described herein may be used for various wirelesscommunications systems such as code division multiple access (CDMA),time division multiple access (TDMA), frequency division multiple access(FDMA), orthogonal frequency division multiple access (OFDMA), singlecarrier frequency division multiple access (SC-FDMA), and other systems.The terms “system” and “network” are often used interchangeably. A codedivision multiple access (CDMA) system may implement a radio technologysuch as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc.CDMA2000 covers IS-2000, IS-95, and IS-856 standards. IS-2000 Releases 0and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856)is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data(HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants ofCDMA. A time division multiple access (TDMA) system may implement aradio technology such as Global System for Mobile Communications (GSM).An OFDMA system may implement a radio technology such as Ultra MobileBroadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16(WiMAX), IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part ofUniversal Mobile Telecommunications system (UMTS). 3GPP Long TermEvolution (LTE) and LTE-advanced (LTE-a) are new releases of UniversalMobile Telecommunications System (UMTS) that use E-UTRA. UTRA, E-UTRA,Universal Mobile Telecommunications System (UMTS), LTE, LTE-a, andGlobal System for Mobile communications (GSM) are described in documentsfrom an organization named “3rd Generation Partnership Project” (3GPP).CDMA2000 and UMB are described in documents from an organization named“3rd Generation Partnership Project 2” (3GPP2). The techniques describedherein may be used for the systems and radio technologies mentionedabove as well as other systems and radio technologies. The descriptionherein, however, describes an LTE system for purposes of example, andLTE terminology is used in much of the description above, although thetechniques are applicable beyond LTE applications.

In LTE/LTE-a networks, including such networks described herein, theterm evolved node B (eNB) may be generally used to describe the basestations. The wireless communications system or systems described hereinmay include a heterogeneous LTE/LTE-a network in which different typesof evolved node B (eNBs) provide coverage for various geographicalregions. For example, each eNB or base station may provide communicationcoverage for a macro cell, a small cell, or other types of cell. Theterm “cell” is a 3GPP term that can be used to describe a base station,a carrier or component carrier associated with a base station, or acoverage area (e.g., sector, etc.) of a carrier or base station,depending on context.

Base stations may include or may be referred to by those skilled in theart as a base transceiver station, a radio base station, an accesspoint, a radio transceiver, a NodeB, eNodeB (eNB), Home NodeB, a HomeeNodeB, or some other suitable terminology. The geographic coverage areafor a base station may be divided into sectors making up only a portionof the coverage area. The wireless communications system or systemsdescribed herein may include base stations of different types (e.g.,macro or small cell base stations). The UEs described herein may be ableto communicate with various types of base stations and network equipmentincluding macro eNBs, small cell eNBs, relay base stations, and thelike. There may be overlapping geographic coverage areas for differenttechnologies.

A macro cell generally covers a relatively large geographic area (e.g.,several kilometers in radius) and may allow unrestricted access by UEswith service subscriptions with the network provider. A small cell is alower-powered base station, as compared with a macro cell, that mayoperate in the same or different (e.g., licensed, unlicensed, etc.)frequency bands as macro cells. Small cells may include pico cells,femto cells, and micro cells according to various examples. A pico cell,for example, may cover a small geographic area and may allowunrestricted access by UEs with service subscriptions with the networkprovider. A femto cell may also cover a small geographic area (e.g., ahome) and may provide restricted access by UEs having an associationwith the femto cell (e.g., UEs in a closed subscriber group (CSG), UEsfor users in the home, and the like). An eNB for a macro cell may bereferred to as a macro eNB. An eNB for a small cell may be referred toas a small cell eNB, a pico eNB, a femto eNB, or a home eNB. An eNB maysupport one or multiple (e.g., two, three, four, and the like) cells(e.g., component carriers). A UE may be able to communicate with varioustypes of base stations and network equipment including macro eNBs, smallcell eNBs, relay base stations, and the like.

The wireless communications system or systems described herein maysupport synchronous or asynchronous operation. For synchronousoperation, the base stations may have similar frame timing, andtransmissions from different base stations may be approximately alignedin time. For asynchronous operation, the base stations may havedifferent frame timing, and transmissions from different base stationsmay not be aligned in time. The techniques described herein may be usedfor either synchronous or asynchronous operations.

The downlink transmissions described herein may also be called forwardlink transmissions while the uplink transmissions may also be calledreverse link transmissions. Each communication link describedherein—including, for example, wireless communications system 100 andsubsystem 200 of FIGS. 1 and 2—may include one or more carriers, whereeach carrier may be a signal made up of multiple sub-carriers (e.g.,waveform signals of different frequencies). Each modulated signal may besent on a different sub-carrier and may carry control information (e.g.,reference signals, control channels, etc.), overhead information, userdata, etc. The communication links described herein (e.g., communicationlinks 125 of FIG. 1) may transmit bidirectional communications usingfrequency division duplex (FDD) (e.g., using paired spectrum resources)or TDD operation (e.g., using unpaired spectrum resources). Framestructures may be defined for frequency division duplex (FDD) (e.g.,frame structure type 1) and TDD (e.g., frame structure type 2).

The description set forth herein, in connection with the appendeddrawings, describes example configurations and does not represent allthe examples that may be implemented or that are within the scope of theclaims. The term “exemplary” used herein means “serving as an example,instance, or illustration,” and not “preferred” or “advantageous overother examples.” The detailed description includes specific details forthe purpose of providing an understanding of the described techniques.These techniques, however, may be practiced without these specificdetails. In some instances, well-known structures and devices are shownin block diagram form in order to avoid obscuring the concepts of thedescribed examples.

In the appended figures, similar components or features may have thesame reference label. Further, various components of the same type maybe distinguished by following the reference label by a dash and a secondlabel that distinguishes among the similar components. If just the firstreference label is used in the specification, the description isapplicable to any one of the similar components having the same firstreference label irrespective of the second reference label.

Information and signals described herein may be represented using any ofa variety of different technologies and techniques. For example, data,instructions, commands, information, signals, bits, symbols, and chipsthat may be referenced throughout the above description may berepresented by voltages, currents, electromagnetic waves, magneticfields or particles, optical fields or particles, or any combinationthereof.

The various illustrative blocks and modules described in connection withthe disclosure herein may be implemented or performed with ageneral-purpose processor, a DSP, an ASIC, an FPGA or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor may be a microprocessor,but in the alternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices (e.g., a combinationof a digital signal processor (DSP) and a microprocessor, multiplemicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration).

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described above can be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations. Also, as used herein, including in the claims, “or” as usedin a list of items (for example, a list of items prefaced by a phrasesuch as “at least one of” or “one or more of”) indicates an inclusivelist such that, for example, a list of at least one of A, B, or C meansA or B or C or AB or AC or BC or ABC (i.e., A and B and C).

Computer-readable media includes both non-transitory computer storagemedia and communication media including any medium that facilitatestransfer of a computer program from one place to another. Anon-transitory storage medium may be any available medium that can beaccessed by a general purpose or special purpose computer. By way ofexample, and not limitation, non-transitory computer-readable media cancomprise RAM, ROM, electrically erasable programmable read only memory(EEPROM), compact disk (CD) ROM or other optical disk storage, magneticdisk storage or other magnetic storage devices, or any othernon-transitory medium that can be used to carry or store desired programcode means in the form of instructions or data structures and that canbe accessed by a general-purpose or special-purpose computer, or ageneral-purpose or special-purpose processor. Also, any connection isproperly termed a computer-readable medium. For example, if the softwareis transmitted from a website, server, or other remote source using acoaxial cable, fiber optic cable, twisted pair, digital subscriber line(DSL), or wireless technologies such as infrared, radio, and microwave,then the coaxial cable, fiber optic cable, twisted pair, digitalsubscriber line (DSL), or wireless technologies such as infrared, radio,and microwave are included in the definition of medium. Disk and disc,as used herein, include CD, laser disc, optical disc, digital versatiledisc (DVD), floppy disk and Blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations of the above are also included within the scope ofcomputer-readable media.

The description herein is provided to enable a person skilled in the artto make or use the disclosure. Various modifications to the disclosurewill be readily apparent to those skilled in the art, and the genericprinciples defined herein may be applied to other variations withoutdeparting from the scope of the disclosure. Thus, the disclosure is notto be limited to the examples and designs described herein but is to beaccorded the broadest scope consistent with the principles and novelfeatures disclosed herein.

What is claimed is:
 1. A method of wireless communication, comprising:determining a duplexing configuration of a carrier; receiving a masterinformation block (MIB) on the carrier; and interpreting at least onefield of the MIB based at least in part on the duplexing configurationof the carrier.
 2. The method of claim 1, wherein the duplexingconfiguration comprises one of a time division duplex (TDD)configuration, a frequency division duplex (FDD), or an unlicensedspectrum configuration.
 3. The method of claim 2, wherein the at leastone field of the MIB comprises a special subframe configuration.
 4. Themethod of claim 3, wherein the special subframe configuration comprisesa reduced downlink pilot time slots (DwPTS) set.
 5. The method of claim1, wherein the at least one field of the MIB comprises one of anindication of a system information block (SIB) location field or anindication of a number of repetitions of the SIB location field.
 6. Themethod of claim 5, wherein the SIB location field is indicative of oneor more downlink (DL) subframe options for SIB1.
 7. The method of claim2, further comprising: postulating a special subframe configurationbased at least in part on the TDD configuration of the carrier, whereinthe MIB is received according to the postulated special subframeconfiguration.
 8. The method of claim 7, wherein the postulated specialsubframe configuration comprises an eleven-symbol downlink pilot timeslot (DwPTS), a nine-symbol DwPTS, a one-symbol guard period, atwo-symbol uplink pilot time slot (UpPTS), or any combination thereof.9. The method of claim 7, further comprising: updating the postulatedspecial subframe configuration based at least in part on the receivedMIB.
 10. The method of claim 1, further comprising: receiving one ormore synchronization signals, wherein the duplexing configuration isdetermined based at least in part on the one or more synchronizationsignals.
 11. The method of claim 1, wherein the at least one field ofthe MIB comprises a duplex configuration-specific field.
 12. A method ofwireless communication, comprising: identifying a duplexingconfiguration of a carrier; configuring a MIB with at least one fieldbased at least in part on the duplexing configuration; and broadcastingthe MIB on the carrier.
 13. The method of claim 12, further comprising:transmitting one or more synchronization signals based at least in parton the duplexing configuration.
 14. The method of claim 12, wherein theduplexing configuration comprises one of a time division duplex (TDD)configuration, a frequency division duplex (FDD) configuration, or anunlicensed spectrum configuration.
 15. The method of claim 14, whereinthe at least one field of the MIB comprises a special subframeconfiguration.
 16. The method of claim 14, wherein the at least onefield of the MIB comprises one of an indication of a system informationblock (SIB) location field or an indication of a number of repetitionsof the SIB location field.
 17. An apparatus for wireless communication,comprising: means for determining a duplexing configuration of acarrier; means for receiving a master information block (MIB) on thecarrier; and means for interpreting at least one field of the MIB basedat least in part on the duplexing configuration of the carrier.
 18. Theapparatus of claim 17, wherein the duplexing configuration comprises oneof a time division duplex (TDD) configuration, a frequency divisionduplex (FDD) configuration, or an unlicensed spectrum configuration. 19.The apparatus of claim 18, wherein the at least one field of the MIBcomprises a special subframe configuration.
 20. The apparatus of claim19, wherein the special subframe configuration comprises a reduceddownlink pilot time slots (DwPTS) set.
 21. The apparatus of claim 18,wherein the at least one field of the MIB comprises one of an indicationof a system information block (SIB) location field or an indication of anumber of repetitions of the SIB location field.
 22. The apparatus ofclaim 21, wherein the SIB location field is indicative of one or moredownlink (DL) subframe options for SIB1.
 23. The apparatus of claim 18,further comprising: means for postulating a special subframeconfiguration based at least in part on the TDD configuration of thecarrier, wherein the MIB is received according to the postulated specialsubframe configuration.
 24. The apparatus of claim 23, wherein thepostulated special subframe configuration comprises an eleven-symboldownlink pilot time slot (DwPTS), a nine-symbol DwPTS, a one-symbolguard period, a two-symbol uplink pilot time slot (UpPTS), or anycombination thereof.
 25. The apparatus of claim 23, further comprising:means for updating the postulated special subframe configuration basedat least in part on the received MIB.
 26. The apparatus of claim 17,further comprising: means for receiving one or more synchronizationsignals, wherein the duplexing configuration is determined based atleast in part on the one or more synchronization signals.
 27. Theapparatus of claim 17, wherein the at least one field of the MIBcomprises a duplex configuration-specific field.
 28. An apparatus forwireless communication, comprising: means for identifying a duplexingconfiguration of a carrier; means for configuring a MIB with at leastone field based at least in part on the duplexing configuration; andmeans for broadcasting the MIB on the carrier.
 29. The apparatus ofclaim 28, further comprising: means for transmitting one or moresynchronization signals based at least in part on the duplexingconfiguration.
 30. The apparatus of claim 28, wherein the duplexingconfiguration comprises one of a time division duplex (TDD)configuration, a frequency division duplex (FDD) configuration, or anunlicensed spectrum configuration.
 31. The apparatus of claim 30,wherein the at least one field of the MIB comprises a special subframeconfiguration.
 32. The apparatus of claim 30, wherein the at least onefield of the MIB comprises one of an indication of a system informationblock (SIB) location field or an indication of a number of repetitionsof the SIB location field.
 33. An apparatus for wireless communication,comprising: a processor; memory in electronic communication with theprocessor; and instructions stored in the memory and operable, whenexecuted by the processor, to cause the apparatus to: determine aduplexing configuration of a carrier; receive a master information block(MIB) on the carrier; and interpret at least one field of the MIB basedat least in part on the duplexing configuration of the carrier.
 34. Theapparatus of claim 33, wherein the duplexing configuration comprises oneof a time division duplex (TDD) configuration, a frequency divisionduplex (FDD) configuration, or an unlicensed spectrum configuration. 35.The apparatus of claim 34, wherein the at least one field of the MIBcomprises a special subframe configuration.
 36. The apparatus of claim35, wherein the special subframe configuration comprises a reduceddownlink pilot time slots (DwPTS) set.
 37. The apparatus of claim 34,wherein the at least one field of the MIB comprises one of an indicationof a system information block (SIB) location field or indication of anumber of repetitions of the SIB location field.
 38. The apparatus ofclaim 37, wherein the SIB location field is indicative of one or moredownlink (DL) subframe options for SIB1.
 39. The apparatus of claim 34,wherein the instructions are operable to cause to: postulate a specialsubframe configuration based at least in part on the TDD configurationof the carrier, wherein the MIB is received according to the postulatedspecial subframe configuration.
 40. The apparatus of claim 39, whereinthe postulated special subframe configuration comprises an eleven-symboldownlink pilot time slot (DwPTS), a nine-symbol DwPTS, a one-symbolguard period, a two-symbol uplink pilot time slot (UpPTS), or anycombination thereof.
 41. The apparatus of claim 39, wherein theinstructions are operable to cause to: update the postulated specialsubframe configuration based at least in part on the received MIB. 42.The apparatus of claim 33, wherein the instructions are operable tocause to: receive one or more synchronization signals, wherein theduplexing configuration is determined based at least in part on the oneor more synchronization signals.
 43. The apparatus of claim 33, whereinthe at least one field of the MIB comprises a duplexconfiguration-specific field.
 44. An apparatus for wirelesscommunication, comprising: a processor; memory in electroniccommunication with the processor; and instructions stored in the memoryand operable, when executed by the processor, to cause the apparatus to:identify a duplexing configuration of a carrier; configure a MIB with atleast one field based at least in part on the duplexing configuration;and broadcast the MIB on the carrier.
 45. The apparatus of claim 44,wherein the instructions are operable to cause to: transmit one or moresynchronization signals based at least in part on the duplexingconfiguration.
 46. The apparatus of claim 44, wherein the duplexingconfiguration comprises one of a time division duplex (TDD)configuration, a frequency division duplex configuration (FDD), or anunlicensed spectrum configuration.
 47. The apparatus of claim 46,wherein the at least one field of the MIB comprises a special subframeconfiguration.
 48. The apparatus of claim 46, wherein the at least onefield of the MIB comprises one of an indication of a system informationblock (SIB) location field or an indication of a number of repetitionsof the SIB location field.
 49. A non-transitory computer-readable mediumstoring code for wireless communication, the code comprisinginstructions executable to: determine a duplexing configuration of acarrier; receive a master information block (MIB) on the carrier; andinterpret at least one field of the MIB based at least in part on theduplexing configuration of the carrier.
 50. The non-transitorycomputer-readable medium of claim 49, wherein the duplexingconfiguration comprises one of a time division duplex (TDD)configuration, a frequency division duplex (FDD) configuration, or anunlicensed spectrum configuration.
 51. The non-transitorycomputer-readable medium of claim 50, wherein the at least one field ofthe MIB comprises a special subframe configuration.
 52. Thenon-transitory computer-readable medium of claim 51, wherein the specialsubframe configuration comprises a reduced downlink pilot time slots(DwPTS) set.
 53. The non-transitory computer-readable medium of claim50, wherein the at least one field of the MIB comprises one of anindication of a system information block (SIB) location field or anindication of a number of repetitions of the SIB location field.
 54. Thenon-transitory computer-readable medium of claim 53, wherein the SIBlocation field is indicative of one or more downlink (DL) subframeoptions for SIB1.
 55. The non-transitory computer-readable medium ofclaim 50, wherein the instructions are executable to: postulate aspecial subframe configuration based at least in part on the TDDconfiguration of the carrier, wherein the MIB is received according tothe postulated special subframe configuration.
 56. The non-transitorycomputer-readable medium of claim 55, wherein the postulated specialsubframe configuration comprises an eleven-symbol downlink pilot timeslot (DwPTS), a nine-symbol DwPTS, a one-symbol guard period, atwo-symbol uplink pilot time slot (UpPTS), or any combination thereof.57. The non-transitory computer-readable medium of claim 55, wherein theinstructions are executable to: update the postulated special subframeconfiguration based at least in part on the received MIB.
 58. Thenon-transitory computer-readable medium of claim 49, wherein theinstructions are executable to: receive one or more synchronizationsignals, wherein the duplexing configuration is determined based atleast in part on the one or more synchronization signals.
 59. Thenon-transitory computer-readable medium of claim 49, wherein the atleast one field of the MIB comprises a duplex configuration-specificfield.
 60. A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable to:identify a duplexing configuration of a carrier; configure a MIB with atleast one field based at least in part on the duplexing configuration;and broadcast the MIB on the carrier.
 61. The non-transitorycomputer-readable medium of claim 60, wherein the instructions areexecutable to: transmit one or more synchronization signals based atleast in part on the duplexing configuration.
 62. The non-transitorycomputer-readable medium of claim 60, wherein the duplexingconfiguration comprises a time division duplex (TDD) configuration, afrequency division duplex (FDD) configuration, or an unlicensed spectrumconfiguration.
 63. The non-transitory computer-readable medium of claim62, wherein the at least one field of the MIB comprises a specialsubframe configuration.
 64. The non-transitory computer-readable mediumof claim 62, wherein the at least one field of the MIB comprises one ofan indication of a SIB location field or an indication of a number ofrepetitions of the SIB location field.